Change Log Entries

The effective date for all products within the scope of this document for this release is April 8th. This release utilizes Expere Engine version 2016.1.0.

Expere Engine updated to latest version of Apache Commons-Collections

  • Reference: PBI 372328
  • Compliance Impacts: This enhancement is not a compliance or regulatory issue.
  • Documentation: No document impact.

The Apache Commons-Collections used with the Expere Engine has been upgraded to version 4.1. For detailed information on JDK classes, consult the Commons-Collections User Guide.

Expere supported to use to Oracle 12

Expere has been validated for use with Oracle 12; for more information, and for a comprehensive list of supported requirements, see Windows Environment Software Requirements and Java Environment Software Requirements.

Barcode spacing issue resolved

  • Reference: PBI 355603
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation: No document impact.

Issue: Previously, the Expere Engine reserved space for ancillary barcodes on dynamic documents even though the barcode element was not included in the .REQ file.

Solution: This issue has been resolved; when generating a dynamic document and selecting an ancillary barcode option, the document will no longer reserve space for the barcode if the .REQ file does not contain a barcode element.

First page only barcode feature added

  • Reference: PBI 364255
  • Compliance Impacts: This new feature is not a compliance or regulatory issue.
  • Documentation: Select And Generate and Generate.

Summary: Users can now apply a barcode to the first or only page of a document. For detailed information on using this feature within the Document Generation Services Tool Suite, see the Select And Generate and Generate webhelp sections within the SERVICE Page.

Note: This feature is NOT fully functional and will be available in a future release.

Missing SaveInResponse element resolved

  • Reference: PBI 368079
  • Compliance Impacts: This defect is not a compliance or regulator issue.
  • Documentation: No document impact.

Previously, the SaveInResponse element was missing from the SelectResponse.xsd file but was still being returned in the response.

This issue has been resolved; the SaveInDatabase element is now an optional element in the SelectResponse.xsd file.

Expere logging enhancements

  • Reference: PBI 360148
  • Compliance Impacts: This enhancement is not a compliance or regulatory issue.
  • Documentation: No document impact.

Summary: The Expere logs have been enhanced to include the DGS ID as the Request ID. The Request ID is now added to all log entries

Expere Engine: Expere upgraded to use Ehcache - 2.10.0

  • Reference: PBI 350323
  • Compliance Impacts: This enhancement is not a compliance or regulatory issue.
  • Documentation: No document impact.

Expere has upgraded to Ehcache 2.10.0 to improve Document Generation Services transaction performance. Ehcache 2.10.0 can be used to determine the following:

  • amount of space in the JRE Heap
  • amount of space outside the JRE Heap
  • amount of disk space

This feature requires an Expere Engine update.

Expere Engine: ehcache: Caching enhanced

Summary: Expere has upgraded to Ehcache 2.10.0 to utilize enhanced caching capability; the following enhancements have been implemented for ehcache.xml:

  • Enhancement #1: Previously there was only one level of cache on objects. Changes have been made to include two cache levels and to add images to the updated cache configuration.
  • Enhancement #2: Cache memory allocation has changed in ehcache.xml. Previously, users could change the maxElementsInMemory value in the global cache (ExpereCache) or any of its smaller caches.

Now, users can adjust the maxBytesLocalHeap and maxBytesLocaldisk values in ExpereCache and its smaller caches. maxBytesLocalHeap is the percentage of allocated Java Virtual Machine (JVM) heap size while maxBytesLocalDisk allocates a specified amount of memory of the local disk for overflow caching.

For detailed information on how to change the memory allocations in the configuration file, see the Expere Implementation Guide: Caching notes.

This feature requires an Expere Engine update.

Expere Engine: OutputFormat printing issue addressed

  • Reference: PBI 322811
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation: No document impact.

The following issues were reported:

  • Mapping "USA" to the "/Txn/OrgEstablishedState" enumeration printed USA on documents when selecting the "Texas" output format; the expected value should have been United States of America.
  • Mapping "NT" to the"Txn/OrgEstablishedState" enumeration printed NW Territories on documents when selecting the "Texas" output format; the expected value should have been Northwest Territories.

The issues above have been resolved. The following now print correctly on all forms:

  • United Stateds of America
  • Northwest Territories

This feature requires a Requirements Editor Tool and Expere Engine update.

Expere Engine: Smart quotes special characters in transaction issue resolved

  • Type: Defect correction
  • Reference: PBI 257585
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation: No document impact.
Summary: It was reported that special characters 0145, 0146, 0147, and 0148 resulted in errors on static documents. See the Expere log example below for more information.

Expere log example
‘ Opening single smart quote Alt 0145 C1 Error
’ Closing single smart quote Alt 0146 C1 Error
“ Opening double smart quote Alt 0147 C1 Error
” Closing double smart quote Alt 0148 C1 Error

Solution: Quotation marks are now converted appropriately (from smart quotes to regular quotes); as a result, static and dynamic documents do not produce an error when generating a .PDF document if smart quotes are present.

This feature requires an Expere Engine update.

Stylesheets: Ancillary Barcode printing over tagline resolved

  • Reference: PBI 355602
  • Compliance Impacts: This defect is not a compliance or regulatory issue.
  • Documentation: No document impact.

Users reported that the ancillary barcode printed over the document tagline on certain documents from the October content release.

Note: No issues existed with TRID or static documents.

There was a change made to the WKFS_StyleGuide. Now the barcodes will no longer render over the top of a footer or tagline.

This feature requires a content stylesheet update which will be available in the November content.